Client interface script based user communication in a mobile network

ABSTRACT

In a mobile network comprising a gateway for establishing a packet data connection with a user equipment, user communication is implemented on the basis of a client interface script to be executed in a browser application of the user equipment. For this purpose, the gateway receives data destined to the browser application of the user equipment. The gateway modifies the received data to provide the user equipment with the client interface script, e.g., by including an identifier of the client interface script in to the data. The gateway sends the modified data to the user equipment, thereby enabling the browser application of the user equipment to execute the client interface script. Execution of the client interface script in the browser application may for example implement a user dialogue for customizing functions of the mobile network.

TECHNICAL FIELD

The present invention relates to methods for user communication in amobile network and to corresponding devices.

BACKGROUND

Smart devices, e.g., laptops and smartphones, have created a new type ofchallenge to mobile networks because these devices may keep a more orless permanent data connection to the mobile network. This may forexample lead to increased signaling in the network. Further, this mayalso lead to increased traffic volume in the mobile network. Inaddition, new features of smart devices have a tendency to increase thedata traffic of mobile network users, e.g., through applicationdownloads or video streaming. At the same time, end users are demandinga better end to end quality of experience (QoE). To address this demandfor improved QoE, mobile networks provide mechanisms for controlling theQuality of Service (QoS) provided for data traffic related to certainservices, e.g., Voice over Internet Protocol (VoIP) telephony ormultimedia service.

In order to manage usage of network resources, mobile networks accordingto the 3^(rd) Generation Partnership Project (3GPP) are provided with aPolicy and Charging Control (PCC) architecture, see, e.g., 3GPPTechnical Specification (TS) 23.203. The PCC architecture allows theoperators to achieve real-time control of their network resources,control subscriber access to services, and proactively optimize networkcapacity. Currently, an end user, i.e., a subscriber accessing themobile network with a user equipment (UE), can customize some PCCfunctions. For example, this can be achieved by a call to a customerservice center. However, other possibilities of interaction between theend user and the PCC architecture are limited.

Accordingly, there is a general need for techniques which providepossibilities of communication between a network node of the mobilenetwork and an end user, e.g., for interactively configuring networkfunctions such as the above-mentioned PCC functions.

SUMMARY

According to an embodiment of the invention, a method is provided. Themethod is to be performed in a mobile network comprising a gateway forestablishing a packet data connection with a user equipment and may beimplemented by the gateway. According to the method, the gatewayreceives data destined to a browser application of the user equipment.The gateway modifies the received data to provide the user equipmentwith a client interface script to be executed in the browser applicationof the user equipment. Further, the gateway sends the modified data tothe user equipment, thereby enabling the browser application to executethe client interface script.

According to a further embodiment of the invention, a method isprovided. The method is to be performed in a mobile network comprising agateway for establishing a packet data connection with a user equipmentand may be implemented by a policy controller of the mobile network.According to this method, the policy controller receives, from thegateway, an indication of data communicated with a browser applicationof the user equipment. Further, the policy controller determines aclient interface script to be executed in the browser application of theuser equipment and sends an identifier of the client interface script tothe gateway.

According to a further embodiment of the invention, a gateway isprovided. The gateway is for use in a mobile network for establishing apacket data connection with a user equipment. The gateway comprises afirst interface with respect to a web server, a second interface withrespect to the user equipment, and a processor. The processor isconfigured to:

receive, via the first interface, data destined to a browser applicationof the user equipment,

modify the received data to provide the user equipment with a clientinterface script to be executed in the browser application to the userequipment, and

send, via the second interface, the modified data to the user equipment,thereby enabling the browser application of the user equipment toexecute the client interface script.

According to a further embodiment of the invention, a policy controlleris provided. The policy controller is for use in a mobile networkcomprising a gateway for establishing a packet data connection with auser equipment. For example, the policy controller may have the purposeof controlling the gateway. The policy controller comprises a controlinterface with respect to the gateway and a processor. The processor isconfigured to:

receive, via the control interface, an indication of data communicatedwith a browser application of the user equipment, and

determine a client interface script to be included in said data and tobe executed in the browser application to the user equipment.

According to further embodiments, other methods, devices, or computerprogram products for implementing the methods may be provided.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a mobile network environment in whichconcepts according to embodiments of the invention can be applied.

FIG. 2 schematically illustrates a PCC architecture according to anembodiment of the invention.

FIG. 3 shows a signaling diagram for illustrating a process according toan embodiment of the invention.

FIG. 4 shows an example of data destined to a browser application.

FIG. 5 shows the data of FIG. 4 as modified in an exemplary processaccording to an embodiment of the invention.

FIG. 6 shows the data of FIG. 4 as modified in a further exemplaryprocess according to an embodiment of the invention.

FIG. 7 schematically illustrates an example of a client interface asgenerated by a CIS in a process according to an embodiment of theinvention.

FIG. 8 shows a signaling diagram for illustrating a further processaccording to an embodiment of the invention.

FIG. 9 shows a signaling diagram for illustrating a still furtherprocess according to an embodiment of the invention.

FIG. 10 schematically illustrates a gateway according to an embodimentof the invention.

FIG. 11 schematically illustrates a policy controller according to anembodiment of the invention.

FIG. 12 shows a flowchart for illustrating a method according to anembodiment of the invention.

FIG. 13 shows a flowchart for illustrating a further method according toan embodiment of the invention.

FIG. 14 shows a flowchart for illustrating a still further methodaccording to an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following, the invention will be explained in more detail byreferring to exemplary embodiments and to the accompanying drawings. Theillustrated embodiments relate to concepts of user communication in amobile network. In particular, the concepts may be used to provide auser with ways to interact with control nodes in the mobile network. Inthe following, the concepts will be explained in the context of a mobilenetwork according to 3GPP TSs. However, it is to be understood that theillustrated concepts may be applied in other types of mobile network aswell.

FIG. 1 schematically illustrates a mobile network environment in whichconcepts according to embodiments of the invention can be applied.

The mobile network environment includes a UE 10, e.g., a mobileterminal, and a number of network components 22, 24, 26, 30. Among thesenetwork components there is a Radio Access Network (RAN) 22. The RAN isbased on a certain type or certain types of radio access technology,e.g. GSM (Global System for Mobile Communications), EDGE (Enhanced DataRate for GSM Evolution), UMTS (Universal Mobile TelecommunicationsSystem), HSPA (High Speed Packet Access), LTE (Long Term Evolution), orLTE-Advanced. Although the RAN 22 is illustrated as a single node, it isto be understood that the RAN 22 may actually be formed of a number ofcomponents, which are not further explained herein. The RAN 22 iscoupled to a transport node 24, which in turn is coupled to a gateway(GW) 26. Here, it is to be understood that alternatively more than onetransport node 24 may be coupled between the RAN 22 and the gateway 26or that the RAN 22 may be directly coupled to the gateway 26. Thegateway 26 may be a Gateway GPRS Support Node (GGSN) providing aconnection of GPRS-based services to one or more external packet datanetworks. The gateway 26 may also be a System Architecture EvolutionGateway (SAE GW) according to the 3GPP TSs.

In addition, the mobile communication network includes a policycontroller 30, which is implemented as a Policy and Charging RulesFunction (PCRF) according to the 3GPP TSs. The policy controller 30 maybe implemented by dedicated hardware and/or comprise software functionsexecuted by a processor. The gateway 26 and the policy controller 30 aretypically regarded as components of a core network. The policycontroller 30 communicates with the gateway 26 via a signaling path 6,which may be implemented using the Gx reference point according to the3GPP TSs. The policy controller 30 may be further coupled to arepository 38 via a signaling path 8, e.g., implemented using the Spreference point according to the 3GPP TSs. The repository 38 may storeuser related subscription data, e.g., arranged in the form of subscriberprofiles and service policies.

As further illustrated, data traffic between the network and the userequipment 10 can be carried by a number of bearers 52, 54. The datatraffic typically pertains to one or more client/peer applications 12running on the UE 10, e.g., may relate to certain services. Theclient/peer applications 12 include at least a browser applicationconfigured to provide a user of the UE 10 with access to resources inthe internet, e.g., to webpages.

The bearers 52, 54 are established between the user equipment 10 and thegateway 26. The bearers 52, 54 carry data traffic in both the DL and theUL direction, i.e., may also be regarded as being formed of a DL bearerand a UL bearer. For supporting bidirectional communication on thebearers 52, 54, the UE 10 is provided with a corresponding interface 15which allows for receiving incoming data packets from the bearers 52, 54and sending outgoing data packets on the bearers 52, 54. Similarly, thegateway 26 is provided with a corresponding interface 25 which allowsfor receiving incoming data packets from the bearers 52, 54 and sendingoutgoing data packets on the bearers 52, 54.

The bearers 52, 54 may include a default bearer 52 generally establishedfor offering packet-based services to the user equipment 10 and,optionally, one or more dedicated bearer 54 which may have different QoSlevel, e.g., a higher or lower QoS level, than the default bearer. Thedefault bearer 52 is typically established when the UE 10 attaches tothe gateway 26. The dedicated bearer may be established on demand, e.g.,when data packets of selected data traffic requiring a certain QoS levelneed to be transmitted.

Each bearer 52, 54 may be associated with a corresponding QoS profile.The QoS profile may be defined through QoS parameters such as a QoSClass Identifier (QCI), an Allocation/Retention Priority (ARP), aTraffic Handling Priority (THP), a Maximum Bit Rate (MBR), an AggregateMaximum Bit Rate (AMBR), and/or a Guaranteed Bit Rate (GBR).Accordingly, a certain QoS level may be provided for communicating datapackets between the UE 10 and the gateway 26 by directing the datapackets to a corresponding bearer.

In the UE 10, the data packets are directed to a desired bearer 52, 54using correspondingly configured UL packet filters 62, 64. In thegateway 26, the data packets are directed to the desired bearers 52, 54using correspondingly configured DL packet filters 72, 74. Parameters ofthe QoS profile may be signaled from the policy controller 30 to thegateway 26 using the signaling path 6. Similarly, the DL packet filters72, 74 to be used in the gateway 26 may be signaled from the policycontroller 30 to the gateway 26 using the signaling path 6. As regardsthe UL packet filters 62, 64 used in the UE 10, these may be signaledfrom the policy controller 30 via the gateway 26 to the UE 10.

In the following, concepts according to embodiments of the inventionwill be explained, which provide a way of communication between one ormore nodes in the mobile network and an end user of the UE 10. Inparticular, these concepts may be applied to provide the end user with amechanism to interact with a control node in the mobile network, e.g.,to modify policy control parameters or traffic handling rules as appliedby the policy controller 30, in the following also referred to as PCCrules. These concepts are based on modifying data destined to thebrowser application running on the UE 10 to provide the UE 10 with aclient interface script (CIS) to be executed in the browser application.More specifically, the gateway 26 may receive the data destined to thebrowser application, modify the received data, and send the modifieddata to the UE 10, thereby enabling the browser application of the UE 10to execute the CIS. Here, it should be noted that the modified data mayinclude the CIS itself or may include an identifier of the CIS, which isthen used by the browser application to obtain the CIS. In somescenarios, execution of the CIS in the browser application may provideinformation to the user, e.g., concerning a service agreement of theuser with an operator of the mobile network. For example, the user couldbe informed of changed bandwidths or tariffs. In some scenarios,execution of the CIS in the browser application may be used forimplementing a user dialogue, i.e., for providing information from anode of the mobile network to the user and vice versa. For example, theuser could be informed of an option concerning a service agreement ofthe user with the operator of the mobile network, and the user couldthen select this option or not. The CIS could then return theinformation concerning the selection to the mobile network. For example,the user could select an option of increased bandwidth for packet dataconnections, an option of increased QoS for certain types of data, anoption of blocking certain types of data, e.g., to implement parentalcontrol, or the like. The CIS may be implemented by any suitableclient-side language, e.g., JavaScript or AJAX (Asynchronous JavaScriptand XML) programming, that can be executed by the browser application.

The concepts may be used to allow the user to customize various types ofPCC rules or parameters thereof, such as: traffic bandwidth for specificfiles, services, applications; a time schedule to apply this bandwidth;new tariffs to be applied or fees for specific files; enabling ordisabling services or applications; and/or parental control. By means ofthe CIS, the user may indicate at any moment how to customize the PCCrules to the mobile network. On the other hand, the mobile networkcontrols the CIS and its provision to the UE 10, and the mobile networkcan be modify the CIS at any suitable moment for PCRF, e.g., to includenew options for selection by the user.

FIG. 2 further illustrates implementation of concepts according to anembodiment of the invention in a PCC architecture according to the 3GPPTSs. As illustrated, the PCC architecture includes a gateway (GW) 26, apolicy controller in the form of a PCRF 30, and a repository 38. Thesecomponents may correspond to the gateway 26, the policy controller 30,and the repository 38 as explained in connection with FIG. 1. In theillustrated embodiment, the PCRF 30 is implemented with a CIS controller32. Further, the PCC architecture also includes a Policy ControlEnforcement Function (PCEF) 34 and a CIS traffic processor 36 which areimplemented in the gateway 26. In the illustrated example, therepository 38 corresponds to a Subscriber Profile Repository (SPR).However, it is to be understood that other types of repository could beused as well, e.g., a User Data Repository (UDR). As illustrated, thePCC architecture may also include a Bearer Binding and Event ReportingFunction (BBERF) 39, an Offline Charging System (OFCS) 42, an OnlineCharging System (OCS) 44, and/or an Application Function (AF) 50.

The PCRF 30 is configured to perform policy control decision and flowbased charging control. The PCRF 30 provides network control regardingdetection of service data flows detection, gating, QoS, and flow basedcharging towards the PCEF 34. For this purpose, the PCRF 30 may signalPCC rules to the PCEF 34. The PCEF 34 may be configured to performservice data flow detection, policy enforcement and flow based chargingfunctionalities, which is typically accomplished by applying the PCCrules as signaled by the PCRF 30. Further, the PCEF 34 may alsoimplement functionalities of packet inspection, such as Deep PacketInspection (DPI), and service classification. In this way data packetsmay be classified according to PCC rules defined in the PCEF 34 and beassigned to a certain service.

As further illustrated in FIG. 2, the nodes of the PCC architecture arecoupled to each other by interfaces or reference points termed as Gx,Gxx, Gy, Gz, Sp, and Rx. The Gx reference point resides between the PCRF30 and the gateway 26, and allows for communication between the PCRF 30and the PCEF 34 or CIS traffic processor 36 in the gateway 26. The Gxxreference point resides between the PCRF 30 and the BBERF 39. The Gyreference point resides between the gateway 26 and the OCS 44. The Gzreference point resides between the gateway 26 and the OFCS 42. The Rxreference point resides between the AF 50 and the PCRF 30. The Spreference point resides between the repository 38 and the PCRF. TheDetails concerning the implementation of these interfaces can be foundin the 3GPP TSs, e.g, 3GPP TS 23.203 and 3GPP TS 29.212. It should benoted that different interfaces could be used in other implementations.

The implementation of concepts according to an embodiment of theinvention as explained in the following involves the PCRF 30 with theCIS controller 32, the gateway 26, in particular the PCEF 34 and the CIStraffic processor 36 implemented in the gateway 26, and the repository38. Further, also the end user, i.e., the subscriber using the UE 10 forestablishing a packet data connection to the gateway 26, and the OCS 44may be involved.

In some embodiments of the invention as explained in the following, therepository 38 further includes a CIS repository. This CIS repository maystore CISs to customize the PCC rules. These CISs can be personalizedfor every user or there may be one specific CIS for each subscriberprofile.

In the illustrated implementation, the PCEF 34 may be responsible forenforcing policies with respect to authentication of subscribers,authorization to access and services, and accounting and mobility. ThePCRF 30 may be responsible for managing individual policies definingnetwork, application, and subscriber conditions that must be met inorder to successfully deliver a service or maintain the QoS of a givenservice. The repository 38, which may be a standalone database orintegrated into an existing subscriber database such as a HomeSubscriber Server (HSS), may include information such as entitlements,rate plans, etc. The repository 38 may provide subscription data such asa subscriber's allowed services, a pre-emption priority for each allowedservice, information on a subscriber's QoS parameters, e.g., asubscribed guaranteed bandwidth QoS, a subscriber's charging relatedinformation, e.g., location information relevant for charging, asubscriber category, e.g., whether the subscriber is a gold user to beprovided with a high QoS or a silver or bronze user to be provided withlower QoS.

In embodiments as explained in the following, the CIS is used tocustomize PCC rules to be applied by the PCEF 34. The CIS contains theinterface logic that allows for customizing the PCC rules. However, itis to be understood that the CIS could alternatively or in addition beused for other types of customization of network functions or usercommunication. Also, the embodiments as explained in the followingassume that the CIS is implemented using JavaScript. Using JavaScripthas the benefit that it is supported in widely varying environments andmost browser applications. Here, it is to be understood that othersuitable languages could be used as well for implementing the CIS, e.g.,AJAX programming. In some embodiments, if support of JavaScript or otherlanguage used for implementing the CIS is disabled in the browserapplication, a message may indicate to the end user how to enable thissupport and customization on the basis of the CIS.

In the illustrated embodiments, the end user does not need any specificaction from PCEF 34 to customize the PCC rules because the CIS isexecuted in the browser application of the UE 10. No dedicatedclient/service architecture is needed for interaction between the enduser and the mobile network. The CIS may send information concerningcustomization options selected by the end user to the mobile network,and a node in the mobile network may collect this information to modifythe PCC functions. The CIS can be sent to the browser application of theUE 10 every time when the end user downloads a webpage. Sending of theCIS may also be triggered by only some specifically selected webpages.

In the illustrated embodiments, data destined to the browser applicationof the UE 10 are modified to provide the CIS to the UE 10. For example,data related to a webpage accessed by the browser application may bemodified in order to insert the CIS in the data traffic associated withthe webpage. In the implementation of FIG. 2, this is accomplished bythe CIS traffic processor 36. Here, it should be noted that themodification of the data could also be accomplished by the PCEF 34itself. However, by implementing the CIS traffic processor separatelyfrom the PCEF 34, altering of the end user traffic by the PCEF 34 isavoided. Selection of the appropriate CIS and modification of PCC ruleson the basis of information obtained by the CIS is accomplished by theCIS controller 32 in the PCRF 30.

FIG. 3 shows a signaling diagram for illustrating an exemplary processof providing the CIS to a UE 10. A PCC architecture as explained inconnection with FIG. 2 is assumed, and the process involves the UE 10,the gateway (GW) 26, the PCRF 30, the repository 38, and a web server80.

In the process of FIG. 3, the UE 10 initially connects to a core packetnetwork of the mobile network. This is accomplished by sending a message301 from the UE 10 to the gateway 26. In response to receiving themessage 301, the PCEF 34 of the gateway 26 establishes a first IPConnectivity Access Network (IP-CAN) session or modifies an existingIP-CAN session.

The PCEF 34 of the gateway 26 then sends to the PCRF 30 an initialCredit Control Request (CCR) message 302. In the CCR message 302, aRequest-Type Attribute Value Pair (AVP) may be set to INITIAL_REQUEST.If so-called Gx+ extensions are enabled for the user session, acapability negotiation may then take place between the PCEF 34 and thePCRF 30 to determine proprietary features to be applied. In such acapability negotiation, an indication could be included that the gateway26 is to be provided with the CIS for customizing PCC rules. Thisindication could be in the form of a Gx+ extension. The negotiation mayalso involve exchanging messages 303, 304 with the repository 38, e.g.,for determining a CIS as indicated by step 305.

Determination of the CIS in step 305 may be accomplished on the basis ofsubscriber data from the repository 38. For example, the repository 38could include an identifier location in which the CIS to be used for acertain subscriber is stored, e.g., in the form of a URL. The repository38 could also include other information which may be used forindividualizing a more generic CIS. In principle, all types ofsubscriber data in the repository 38 may be used for determining a CISwhich is suitable for a certain end user.

The PCRF 30 then returns a Credit-Control-Answer (CCA) message 306 tothe gateway 26. Depending on the negotiated capabilities, the CCAmessage 306 includes some form of policy control decision, e.g., whichdetermine user access rights to one or more services. According to theillustrated embodiment, the CCA message 306 may indicate that the enduser of the UE 10 has access to the service of customization of PCCrules and also the location of the CIS. For example, the location of theCIS may be indicated in the form of a Uniform Resource Locator (ULR).

When the end user of the UE 10 starts browsing a web page, the browserapplication of the UE 10 sends a HTTP GET request 307. The HTTP GETrequest 307 is directed to the web server 80, but is initially receivedby the gateway 26. The PCEF 34 in the gateway 26 detects the HTTP GETrequest 307, as indicated by step 308, and forwards it in message 309 tothe web server 80. For detecting the HTTP GET request 307, the PCEF 34in the gateway may for example use DPI or other packet inspectionfunctionalities. The CIS traffic processor 36 in the gateway 26 receivesthe response message 309 from the web server 80, e.g., a HTTP

200 OK message. The response message 309 includes data destined to thebrowser application of the UE 10.

As indicated by step 311, the CIS traffic processor 36 in the gateway 26then modifies the data received from the web server 80. In particular,the CIS traffic processor 36 includes the location of the CIS into thedata, i.e., in the form of the URL as received in message 306.

The CIS traffic processor 36 in the gateway 26 then sends a message 312including the modified data to the UE 10. In the UE 10, the modifieddata are processed by the browser application. Due to the modificationin the data, the browser application causes the UE 10 to obtain the CISfrom the indicated location, as indicated by message 313. In theillustrated example, the CIS is obtained from the repository 38. Theobtained CIS is then executed in the browser application of the UE 10.

In the UE 10, the CIS may be used to show the end user different optionsto configure PCC rules. As will be further explained below, this may beaccomplished in a separate browser application window, with noalteration of the requested webpage, or in the same browser applicationwindow as the requested webpage, which may be accomplished with smallalterations of the requested webpage. The end user of the UE 10 mayselect one or more options presented by the CIS. The selection of anoption may for example be used to select the bandwidth to be applied forfuture traffic related to the requested webpage or to traffic related toa certain URL or HyperText Transfer Protocol (HTTP) service. Also, theselection of one or more options could be used to determine a certaintime for applying the selected bandwidth. Further, the selection of oneor more options could be used to select a tariff to be applied or toconfigure PCC rules related to parental control, a time schedule forapplication of different bandwidths, handling of newly availableservices, application of new commercial packages, etc.

In the above process, the data destined to the browser applicationtypically include HyperText Markup Language (HTML) code. An example ofsuch HTML code is illustrated in FIG. 4. The exemplary HTML code of FIG.4 corresponds to a web page entitled “Example”. An example of amodification of the HTML code of FIG. 5 as accomplished in step 311 ofthe process of FIG. 3 is illustrated in FIG. 5. In FIG. 5, modifiedparts of the HTML code are illustrated in bold characters. The locationof the CIS is indicated by the string“src=http://<SPR_URL>/<MSISDN>.jss”.

In the example of FIG. 5, the modified HTML code uses the “popup”function of JavaScript, which opens a new browser window for the CIS. Inthe browser window, the end user could select one or more options, andinformation concerning this selection could be sent to a web server inthe mobile network. When using the “popup” function, the browser windowwould be independent from the original webpage requested by the enduser.

Another example of a modification is illustrated in FIG. 6. Again, themodified parts of the HTML code are illustrated in bold characters, andthe location of the CIS is indicated by the string“src=http://<SPR_URL>/<MSISDN>.jss”. In the example of FIG. 6, themodified HTML code is configured to launch a popup, referred to as a“form”, in the same browser window as the requested webpage. For thispurpose, AJAX programming of the CIS may be used.

In the example of FIG. 6, the end user may select one or more optionsand submit the form and/or close the popup. Since the CIS is executed inthe same browser window as the requested web page, the informationconcerning the selection by the user would typically be sent to the webserver hosting the webpage. In such an implementation, the PCEF 34 inthe gateway 26 could detect the corresponding message to the web server,and the CIS traffic processor 36 could extract the informationconcerning the selection from the message. The CIS traffic processor 36in the gateway could then remove the message from the traffic to the webserver.

FIG. 7 schematically illustrates a client interface as generated in anembodiment of the invention. More specifically, FIG. 7 illustrates abrowser application display as presented to the end user of the UE 10.The browser application display includes a browser application window400, and a CIS popup 410. The browser application window 400 may be oneof a plurality of browser application windows generated by the browserapplication. The browser application window may be displayed in only apart of a full display area of the UE 10, e.g., together with otherwindows, or may cover the full display area. Also, in some scenariosother windows may overlap the browser application window 400. Thebrowser application window 400 may for example be used to display thewebpage associated with the exemplary HTML code of FIGS. 4 to 6.

As further illustrated, the browser application display also includes aCIS popup 410. In the illustrated example, the CIS popup 410 includesoptions 420 for selection by the end user and information 430 to the enduser. The number of the options 420 may be selected as appropriate.Also, in some scenarios either the options 420 or the information 430could be omitted. As explained above, code controlling the CIS popup 410may be inserted the HTML code of a webpage.

If the browser application generates a new browser window for the CIS,as in the example of FIG. 5, the CIS popup 410 would be a browser windowwhich is separate from the browser window 400. If the browserapplication used a popup in the same browser window for the CIS, as inthe example of FIG. 6, the CIS popup 410 would be a popup within thebrowser window 400.

The CIS popup 410 may be opened at any moment from the webpage that theend user is viewing, e.g., by clicking in a button or a link. In orderto avoid undesired opening of the CIS popup 410, the data destined tothe browser application of the UE 10 could also be modified by the CIStraffic processor to install cookies in the browser application.Information from the cookies could be used to track what options wereselected or rejected in the past or when the CIS was launched in thepast. This may also be used to offer discounts or commercial offersaccording to previously selected options without using any databasewhere saving these previous selections. For example, the end user couldbe offered to get a first video for free but pay for the second one.

The operator of the mobile network may determine when to provide the CISto the UE 10. For example, data related to all webpages requested by thebrowser application of the UE 10 could be modified to provide the CIS tothe UE 10. Alternatively, the CIS could be provided to the UE 10 onlywhen a new service is detected. For example, if the PCEF 34 in thegateway 26 detects that a service such as Facebook, Twitter, a mobilegame, a mobile gambling application is used for the first time by the UE10, the CIS could be provided to the UE 10. Also, if a non-HTTP serviceis detected, such as Skype, instant messaging or mobile television, theCIS may be provided to the UE 10 when the browser application accessesthe next webpage.

The CIS may open a HyperText Transfer Protocol (HTTP) connection to sendthe information concerning the selection by the end user to the mobilenetwork. For example, this may be accomplished using the HTTP POST orthe HTTP GET method. Sending of the information is asynchronous and maybe accomplished in parallel to the HTTP connection used for therequested webpage.

It should be noted that the modification of the data by the CIS trafficprocessor 36 may also include modification of Transport Control Protocol(TCP) sequence numbers. In particular, TCP sequence numbers in themodified traffic to the UE 10 may be replaced to take into account thatthe data as modified in step 311 of FIG. 3 needs a longer message 309than the original message 310 from the web server 80. Also, TCP sequencenumbers in the traffic from the UE 10 to the web server 80 may bereplaced according to what the web server 80 expects, i.e., with TCPsequence numbers as used without modification of the data at step 311.

FIG. 8 shows a signaling diagram for illustrating an exemplary processof sending information obtained by the CIS from the UE 10 to the mobilenetwork. A PCC architecture as explained in connection with FIG. 2 isassumed, and the process involves the UE 10, the gateway (GW) 26, thePCRF 30, an internal web server 60, and the OCS 44. The internal webserver may be implemented in any node of the mobile network which has aconnection to the PCRF 30. For example, the internal web server 60 couldbe implemented in the same node as the repository 38. The internal webserver 60 has the purpose of collecting the information obtained by theCIS. The process of FIG. 8 may be performed when the end user hasselected one or more options in the CIS. For example, the process ofFIG. 8 may follow the process of FIG. 3.

In the process of FIG. 8, the CIS opens a HTTP connection with theinternal web server 60, which is accomplished by sending a message 801.For this purpose, the HTTP GET method or the HTTP POST method may beused. The information concerning the selection by the end user may beHTTP parameters of this HTTP connection. For example, such parameterscould be expressed as “bandwidth=5000, time=30,URL=service=http://www.example.com?q=YF32FF” to indicate that abandwidth of 5000 Mbs should be applied for the next 30 min and for HTTPtraffic related to the URL www.example.com?q=YF32FF.

As indicated by step 802, the internal web server 60 determinesparameters from the message 801, e.g. a selected bandwith, a selectedtime, a selected URL, or the like. The internal web server 60 thencommunicates the parameters to the PCRF 30. This may be accomplished bysending a CCR message 803 to the PCRF 30 and receiving a CCA message 804from the PCRF 30.

At step 805 the PCRF 30 determines new or updated PCC rules on the basisof the parameters received from the internal web server 60. Thisdetermination may also take into account subscriber data or servicepolicies as stored in the repository 38.

The PCRF 30 then sends the determined PCC rules to the gateway 26, wherethey are to be applied by the PCEF 34. This may be accomplished byreceiving a CCR message 806 from the gateway 26 and sending a CCAmessage 807 with the PCC rules to the gateway 26.

As indicated by step 806, the PCC rules are installed in the PCEF 34 ofthe gateway 26 and will be applied to future traffic from or to the UE10. For example, the bandwidth for a download could be increased orcertain types of traffic, such as mobile gaming, could be blocked asselected by the end user.

Since other fees may be associated with the newly installed PCC rules,the PCEF 34 of the gateway 26 may inform the OCS 44 accordingly. Thismay be accomplished by sending a CCR message 809 to the OCS 44 andreceiving a CCA message from the OCS 44.

As illustrated with exemplary message 811 and indicated by step 802, thenewly installed PCC rules are then enforced on the data traffic from orto the UE 10. For example, if the newly installed PCC rules includeblocking of traffic related to mobile gaming and the message 811 is arequest related to mobile gaming, enforcing the PCC rules causes themessage 811 to be blocked by the PCEF 34 of the gateway 26.

FIG. 9 shows a signaling diagram for illustrating a further exemplaryprocess of sending information obtained by the CIS from the UE 10 to themobile network. A PCC architecture as explained in connection with FIG.2 is assumed, and the process involves the UE 10, the gateway (GW) 26,the PCRF 30, the OCS 44, and a web server 80. The process of FIG. 9 maybe performed when the end user has selected one or more options in theCIS. For example, the process of FIG. 9 may follow the process of FIG.3. As compared to the process of FIG. 8, no internal web server isneeded in the process of FIG. 9. Rather, the CIS traffic processor 36 inthe gateway 26 may collect the information obtained by the CIS. For thispurpose, the CIS traffic processor 36 may intercept traffic from the UE10 to the web server 80 and extract the information from the interceptedtraffic. Further, the CIS traffic processor 26 may remove the extractedinformation from the the traffic to the web server 80. For this purpose,the CIS traffic processor 36 in the gateway 26 may act, toward the UE10, as a replacement of the web server 80. For example, the CIS trafficprocessor 26 could act as a HTTP proxy. In the process of FIG. 9, thegateway 26 itself could generate new PCC rules on the basis of theextracted information. Alternatively or in addition, the gateway 26could send the extracted information to the PCRF 30 for generation ofnew PCC rules.

In the process of FIG. 9, the CIS opens a HTTP connection with the webserver 80, which is accomplished by sending a message 901. As in theprocess of FIG. 8, the HTTP GET method or the HTTP POST method may beused for this purpose. The information concerning the selection by theend user may be HTTP parameters of this HTTP connection. For example, asin the process of FIG. 8, such parameters could be expressed as“bandwidth=5000, time=30, URL=service=http://www.example.com?q=YF32FF”to indicate that a bandwidth of 5000 Mbs should be applied for the next30 min and for HTTP traffic related to the URL www.example.com?q=YF32FF.

As indicated by step 902, the CIS traffic processor 36 of the gateway 26intercepts this HTTP connection and determines parameters from theintercepted message 901, e.g. a selected bandwith, a selected time, aselected URL, or the like. Other traffic from the UE 10 to the webserver 80 may be forwarded to the web server 80.

The parameters as determined by the CIS traffic processor 26 could belocally applied in the gateway 26 to generate new or updated PCC rules.In this way, signaling between the gateway and the PCRF 30 could bereduced.

However, as illustrated in FIG. 9, the CIS traffic processor 36 of thegateway may also communicate the determined parameters to the PCRF 30.This may be accomplished by sending a CCR message 904 to the PCRF 30. Asindicated by step 905, the PCRF 30 may then determine new or updated PCCrules on the basis of the received parameters and send these PCC rulesto the PCEF 34 of the gateway 26. This may be accomplished by CCAmessage 906.

As indicated by step 907, the PCC rules are installed in the PCEF 34 ofthe gateway 26 and will be applied to future traffic from or to the UE10. For example, the bandwidth for a download could be increased orcertain types of traffic, such as mobile gaming, could be blocked asselected by the end user.

Since other fees may be associated with the newly installed PCC rules,the PCEF 34 of the gateway 26 may inform the OCS 44 accordingly. Thismay be accomplished by sending a CCR message 908 to the OCS 44 andreceiving a CCA message 909 from the OCS 44.

As illustrated with exemplary message 910 and indicated by step 911, thenewly installed PCC rules are then enforced on the data traffic from orto the UE 10. For example, if the newly installed PCC rules include anincrease of bandwidth for a download from the web server 80, representedby message 910, enforcing the PCC rules causes the bandwidth to beincreased. For example, a dedicated bearer 54 as explained in connectionwith FIG. 1 could be assigned to this download and be configured with acorresponding GBR.

FIG. 10 further illustrates an exemplary implementation of a gateway. Inparticular, the gateway may correspond to the gateway 26 as explainedabove.

In the illustrated example, the gateway 26 includes a backbone interface120 and a data interface 130. The data interface 130 may be used forestablishing a packet data connection to one or more UEs, e.g., to theUE 10 of FIGS. 1, 3, 8, and 9. The backbone interface 120 may be used tocommunicate data with internet resources, e.g., with web servers such asthe web server 80 of FIGS. 3 and 9. In addition, the gateway 26 is alsoprovided with a control interface 140. The control interface 140 may beused for sending and receiving control signaling, e.g., concerningtraffic handling rules. In the illustrated 3GPP scenario, the controlinterface 140 may implement the above-mentioned Gx reference point,e.g., for communication with the PCRF in the processes of FIGS. 8 and 9,Gxx reference point, Gy reference point, e.g., for communication withthe OCS in the process of FIGS. 8 and 9, or Gz reference point.

Further, the gateway 26 includes a processor 150 coupled to theinterfaces 130, 140 and a memory 160 coupled to the processor 150. Thememory 160 may include a read-only memory (ROM), e.g. a flash ROM, arandom-access memory (RAM), e.g. a Dynamic RAM (DRAM) or static RAM(SRAM), a mass storage, e.g., a hard disk or solid state disk, or thelike. The memory 160 includes suitably configured program code to beexecuted by the processor 150 so as to implement the above-describedfunctionalities of the gateway 26 in user communication using a CIS.More specifically, the memory 160 may include a CIS processing module170 so as to implement the above-described functionalities of the CIStraffic processor 36, e.g, modifying data traffic of a UE or extractinginformation from data traffic of a UE. Further, the memory 160 may alsoinclude a control module 180 so as to implement control functionalitiesof the gateway 26. Among these functionalities there may befunctionalities of policy enforcement such as performed by the abovedescribed PCEF 34. The control functionalities may also include packetinspection functionalities such as DPI or the like, e.g., for detectingdata traffic to be modified.

It is to be understood that the structure as illustrated in FIG. 10 ismerely schematic and that the gateway 26 may actually include furthercomponents which, for the sake of clarity, have not been illustrated,e.g., further interfaces. Also, it is to be understood that the memory150 may include further types of program code modules, which have notbeen illustrated, e.g., program code modules for implementing knownfunctionalities of a gateway, e.g., protocol functionalities or thelike. According to some embodiments, also a computer program product maybe provided for implementing concepts according to embodiments of theinvention, e.g., a medium storing the program code to be stored in thememory 160.

FIG. 11 further illustrates an exemplary implementation of a policycontroller. The policy controller may correspond to the policycontroller 30 as explained in connection with FIGS. 1-3, 8, and 9 andmay in particular be implemented as a PCRF as explained in connectionwith FIGS. 2, 3, 8, and 9.

In the illustrated example, the policy controller 30 includes arepository interface 220, an application interface 230, and a controlinterface 240. The repository interface 220 may be used forcommunication with a repository such as the above-mentioned repository38. In the concepts of user communication on the basis of a CIS asdescribed herein, the repository interface 220 may be used for receivingsubscription data from the repository, which may then be used fordetermining the CIS to be provided to the UE. Further, also dataindicating a storage location of the CIS may be obtained via therepository interface 220. In a 3GPP PCC architecture as illustrated inFIG. 2, the repository interface 220 may be implemented as the Spreference point. The application interface 230 may be used forapplication level communication, e.g., with an AF 50 is illustrated inFIG. 2. If the policy controller 30 is implemented as a PCRF accordingto the 3GPP TSs, the application interface 230 may correspond to the Rxreference point. The control interface 240 may be used for sending andreceiving control signaling. If the policy controller 30 is implementedas a PCRF according to the 3GPP TSs, the control interface 240 maycorrespond to the Gx reference point, e.g., for communication with thePCEF 34 or CIS traffic processor 26 in the processes of FIGS. 3, 8 and9. In some scenarios, the control interface 240 may also implement theGxx reference point.

Further, the policy controller 30 includes a processor 250 coupled tothe interfaces 220, 230, 240 and a memory 260 coupled to the processor250. The memory 260 may include a read-only memory (ROM), e.g. a flashROM, a random-access memory (RAM), e.g. a Dynamic RAM (DRAM) or staticRAM (SRAM), a mass storage, e.g., a hard disk or solid state disk, orthe like. The memory 260 includes suitably configured program code to beexecuted by the processor 250 so as to implement the above-describedfunctionalities of the policy controller 30 in user communication usinga CIS. More specifically, the memory 260 may include a CIS determinationmodule 270 so as to implement the above-described functionalities of theCIS controller 32, e.g., for to determining the CIS to be provided tothe UE. As mentioned above, such a determination may be accomplished onthe basis of subscription data, which in the illustrated implementationmay be received via the repository interface 220 from a repositorycoupled thereto. Further, the memory 260 may also include a controlmodule 280 so as to implement control functionalities of the policycontroller. Among these functionalities there may be functionalities ofpolicy control such as performed by a PCRF according to the 3GPP TSs. Inconnection with concepts customization of PCC rules as described above,these functionalities may also include the determination of new orupdated PCC rules on the basis of parameters or other information asobtained by the CIS.

It is to be understood that the structure as illustrated in FIG. 11 ismerely schematic and that the policy controller 30 may actually includefurther components which, for the sake of clarity, have not beenillustrated, e.g., further interfaces. Also, some of the illustratedstructures may be omitted. For example, the application interface 230could be omitted in some embodiments. Also, it is to be understood thatthe memory 250 may include further types of program code modules, whichhave not been illustrated, e.g., program code modules for implementingknown functionalities of a policy controller, e.g., filter generation orthe like. According to some embodiments, also a computer program productmay be provided for implementing concepts according to embodiments ofthe invention, e.g., a medium storing the program code to be stored inthe memory 260.

FIG. 12 shows a flowchart for illustrating a method according to anembodiment of the invention. The method may be used in a mobile networkenvironment as illustrated in FIG. 1 and in particular be implemented ina gateway of the mobile network, which is used for implementing a packetdata connection with a UE, e.g., the above-mentioned UE 10. The methodmay be used to implement parts of the processes as explained inconnection with FIGS. 3, 8, and 9. If the mobile network uses a PCCarchitecture as explained in connection with FIG. 2, the method may beimplemented in the gateway 26, using functionalities of the PCEF 34 andof the CIS traffic processor 36.

At step 1210, the gateway receives data destined to a browserapplication of the UE. The gateway may detect the data by inspectingdata packets, e.g., using packet inspection functionalities. Forexample, the packet inspection functionalities may use DPI, such as inthe above-described PCEF 34 of the gateway 26. The gateway may receivethe data via a corresponding interface, e.g., the backbone interface 220of FIG. 10.

At step 1220, the gateway modifies the received data to provide the UEwith a CIS to be executed in the browser application of the UE. Forexample, this may be accomplished by the above-described CIS trafficprocessor 36. The modification of the data may involve including anidentifier of the CIS into the data, e.g., to specify a location fromwhere the CIS can be obtained. For example, such an identifier could bein the form of a URL. Alternatively, the data could also be modified byinserting the CIS itself. The CIS may be configured for implementing auser dialogue, e.g., as explained in connection with FIGS. 3 and 7.However, the CIS could also be configured to merely provide informationto an end user of the UE. In some embodiments, the modification may bein HTML code destined to the browser application, e.g., as explained inconnection with FIGS. 4 to 6.

At step 1230, the gateway sends the modified data to the UE. This may beaccomplished via a corresponding interface of the gateway, e.g., thedata interface 130 of FIG. 10. In this way, the browser application ofthe UE is enabled to execute the CIS. In some embodiments receiving themodified data may directly cause the browser application to execute theCIS. In other embodiments, the CIS can be executed in the browserapplication in response to some user action, e.g., clicking a button orlink. In some embodiments, the browser application obtains the CIS,e.g., from a location indicated in the modified data, before the CIS isexecuted in the browser application.

Execution of the CIS in the browser application may be used to obtaininformation concerning a selection by an end user of the UE. Thisinformation, e.g., a parameter obtained by the CIS, may be provided bythe CIS to the mobile network, where it can be used as a basis forgenerating one or more new or updated traffic handling rules, such asthe above-mentioned PCC rules. In such a scenario, the gateway mayinstall and apply the new or updated traffic handling rules at step1240. For example, such a new or updated traffic handling rule coulddefine a change in bandwidth to be applied for a certain time. In a 3GPPPCC architecture as explained in connection with FIG. 2, application ofthe new or updated traffic handling rule may for example be accomplishedby a PCEF of the gateway.

FIG. 13 shows a flowchart for illustrating a further method according toan embodiment of the invention. The method may be used in a mobilenetwork environment as illustrated in FIG. 1 and in particular beimplemented in a policy controller of the mobile network. The policycontroller may in turn control a gateway of the mobile network, which isused for establishing packet data connection with a UE, e.g., theabove-mentioned UE 10. The method may be used to implement parts of theprocesses as explained in connection with FIGS. 3, 8, and 9. If themobile network uses a PCC architecture as explained in connection withFIG. 2, the method may be implemented in the PCRF 30.

At step 1310, the policy controller receives an indication of datadestined to a browser application of the UE. The indication is receivedfrom the gateway establishing the packet data connection to the UE. Forexample, such an indication could be generated by packet inspectionfunctionalities of the gateway, such as the DPI functionalities whichmay be implemented in the PCEF 34 of the gateway 26 in the PCCarchitecture of FIG. 2. The indication may be received via a controlinterface of the policy controller, e.g., the control interface 240 ofFIG. 11.

At step 1320, the policy controller determines a CIS to be provided tothe UE. For example, the policy controller may determine the CIS on thebasis of subscription data related to the UE and received from asubscriber data repository, e.g., the repository 38. In this way, theCIS may be individually determined for different end users.

At step 1330, the policy controller sends an identifier of thedetermined CIS to the gateway. The identifier may for example specify alocation from where the CIS can be obtained, e.g., in the form of a URL.The policy controller may send the identifier via a control interface,e.g., the control interface 240 of FIG. 11. The gateway may then use theidentifier to provide the CIS to the UE for execution in the browserapplication, e.g., by modifying data destined to the browser applicationof the UE. The CIS may be configured for implementing a user dialogue,e.g., as explained in connection with FIGS. 3 and 7. However, the CIScould also be configured to merely provide information to an end user ofthe UE. In some embodiments, the modification may be in HTML codedestined to the browser application, e.g., as explained in connectionwith FIGS. 4 to 6.

Execution of the CIS in the browser application may be used to obtaininformation concerning a selection by an end user of the UE. Thisinformation, e.g., a parameter obtained by the CIS, may be provided bythe CIS to the mobile network, where it can be used as a basis forgenerating one or more new or updated traffic handling rules, such asthe above-mentioned PCC rules. In such a scenario, the policy controllermay receive information obtained by the CIS and generate the new orupdated traffic handling rules on the basis of the obtained information.For example, such a new or updated traffic handling rule could define achange in bandwidth to be applied for a certain time. The policycontroller may send the new or updated traffic handling rules to thegateway, where they can be applied to data traffic from or to the UE. Ina 3GPP PCC architecture as explained in connection with FIG. 2,application of the new or updated traffic handling rule may for examplebe accomplished by a PCEF of the gateway.

In some embodiments, the policy controller may receive the informationobtained by the CIS from the gateway, e.g., as in the process of FIG. 9.Alternatively, the policy controller may receive the informationobtained by the CIS from a web server communicating with the UE, e.g.,as in the process of FIG. 8.

FIG. 14 shows a flowchart for illustrating a further method according toan embodiment of the invention. The method may be used in a mobilenetwork environment as illustrated in FIG. 1. The method can be used tocollect information obtained by a CIS in the mobile network and can beimplemented in a web server of the mobile network, e.g., the internalweb server 60 of FIG. 8, or in a gateway of the mobile network, e.g.,the gateway 26, which is used for establishing a packet data connectionwith a UE, e.g., the above-mentioned UE 10. The method may be used toimplement parts of the processes as explained in connection with FIGS. 8and 9.

At step 1410, data generated by execution of the CIS are received fromthe UE executing the CIS. In some embodiments, the data may be receivedby a web server communicating with the UE, e.g., by the internal webserver 60 in the process of FIG. 8. For example, the data may bereceived in a message directed to this web server, e.g., the message 801of FIG. 8. In other embodiments, the data may be received by the gatewayestablishing the packet data connection to the UE executing the CIS,e.g., by the gateway 26 in the process of FIG. 9. For example, the datamay be received to a message directed to a web server, which isintercepted by the gateway, e.g., as the message 901 in the process ofFIG. 9.

At step 1420, information is extracted from the received data. Forexample, this information may include one or more parameters to be usedfor generating one or more new or updated traffic handling rules, e.g.,a modified bandwidth.

In some embodiments, the extracted information is sent to a further nodein step 1430. For example, the information may be sent to a policycontroller of the mobile network, e.g., the PCRF 30 in the process ofFIG. 8 or 9, where the information can be used for generating new orupdated traffic handling rules. This option may in particular be appliedif the information is extracted by the web server.

In other embodiments, the extracted information can also be used locallyin step 1440 for generating one or more new or updated traffic handlingrules. This option may in particular be applied if the information isextracted by the gateway, which also applies traffic handling rules.

It is to be understood that the methods of FIGS. 12 to 14 may becombined to each other as appropriate. For example, the method of FIG.12 may be used to provide a CIS to the UE, which is determined accordingto the method of FIG. 13. Further, the method of FIG. 14 may be appliedin connection with the method of FIG. 12 and/or 13 to collect theinformation obtained by the CIS.

The concepts as explained above can be used as an automatic tool tocustomize functions in a mobile network, e.g., PCC functions. Thisallows for a more individual customization than typical commercialpackages offered by operators of mobile networks. With conceptsaccording to some of the above embodiments, the end user can selectvarious types of options. This can be done at any time the browserapplication is used to access a web page. The selection by the end usermay be applied instantly to ongoing traffic. For example, the end usercan prioritize at any time what traffic is considered to be mostimportant. The end user could select to pay an extra fee to downloaddata using a high bandwidth or select to pay less money to download thesame data using a low bandwidth. The end user could also configure whatwebpages, services, or applications are allowed/forbidden for childrento implement parental control. This could also be accomplished inconnection with a time schedule defining when these webpages, services,or applications are allowed/forbidden. For an operator of the mobilenetwork, concepts as explained above allow for making a more efficientuse of network resources, e.g., by limiting network resources providedfor end users having a subscription on the basis of a low price, andgiving these end users the possibility to override these limitations ifaccording to individual selections. For example, such users could selectto increase a limited bandwidth for a specific file or contents andagree to pay an extra fee for this increase. Further, the concepts asexplained above may also be used to interact with operator services. Forexample, the operator could be advertise an offer or discount throughthe CIS and the if the end user selects to accept the offer or discount,this could be applied instantly.

It is to be understood that the examples and embodiments as explainedabove are merely illustrative and susceptible to various modifications.For example, the concepts could be used in other types of mobile networkenvironment than the described 3GPP implementations. Also, the conceptsmay be applied to various types of interaction between a node in themobile network and an end user of a UE. Further, it is to be understoodthat the above concepts may be implemented by using correspondinglydesigned software to be executed by a processor of an existing device,or by using dedicated device hardware.

1. A method to be performed in a mobile network comprising a gateway forestablishing a packet data connection with a user equipment, the methodcomprising: the gateway receiving data destined to a browser applicationof the user equipment; the gateway modifying the received data toprovide the user equipment with a client interface script to be executedin the browser application of the user equipment; and the gatewaysending the modified data to the user equipment, thereby enabling thebrowser application to execute the client interface script.
 2. Themethod according to claim 1, comprising: the gateway receivinginformation generated by execution of the client interface script. 3.The method according to claim 2, comprising: the gateway receiving aresponse from the user equipment to a web server; and the gatewayextracting the information from the response.
 4. The method according toclaim 2, comprising: the gateway sending the information to a policycontroller of the mobile network.
 5. The method according to claim 2,the gateway receiving the information from a web server communicatingwith the user equipment.
 6. The method according to claim 1, comprising:the gateway installing a traffic handling rule, said traffic handlingrule being generated on the basis of information generated by executionof the client interface script.
 7. The method according to claim 1,comprising: detecting the data destined to the browser application byinspecting data packets.
 8. The method according to claim 1, wherein themodified data include an identifier of the client interface script. 9.The method according to claim 1, wherein the client interface script isconfigured for implementing a user dialogue.
 10. A method to beperformed in a mobile network comprising a gateway for establishing apacket data connection with a user equipment, the method comprising: apolicy controller of the mobile network receiving, from the gateway, anindication of a data communicated with a browser application of the userequipment; the policy controller determining a client interface scriptto be executed in the browser application of the user equipment; and thepolicy controller sending an identifier of the client interface scriptto the gateway.
 11. The method according to claim 10, comprising: thepolicy controller receiving subscription data related to the userequipment from a subscriber data repository; and the policy controllerdetermining the client interface script on the basis of the receivedsubscription data.
 12. The method according to claim 10, comprising: thepolicy controller receiving information generated by execution of theclient interface script; and the policy controller generating, on thebasis of the information, a traffic handling rule.
 13. The methodaccording to claim 12, wherein the policy controller receives theinformation from the gateway.
 14. The method according to claim 12,wherein the policy controller receives the information from a web servercommunicating with the user equipment.
 15. The method according to claim12, comprising: the policy controller sending the traffic handling ruleto the gateway.
 16. The method according to claim 10, wherein the clientinterface script is configured for implementing a user dialogue.
 17. Agateway to be used in a mobile network for establishing a packet dataconnection with a user equipment, the gateway comprising: a firstinterface with respect to a web server; and a second interface withrespect to the user equipment; and a processor; wherein the processor isconfigured to: receive, via the first interface, data destined to abrowser application of the user equipment, modify the received data toprovide the user equipment with a client interface script to be executedin the browser application to the user equipment, and send, via thesecond interface, the modified data to the user equipment, therebyenabling the browser application of the user equipment to execute theclient interface script.
 18. The gateway according to claim 17, whereinthe gateway is configured to install a traffic handling rule that isgenerated based on information generated by execution of the clientinterface script.
 19. A policy controller to be used in a mobile networkcomprising a gateway for establishing a packet data connection with auser equipment, the policy controller comprising: a control interfacewith respect to the gateway; and a processor, wherein the processor isconfigured to: receive, via the control interface, an indication of datacommunicated with a browser application of the user equipment, anddetermine a client interface script to be executed in the browserapplication of the user equipment.
 20. The policy controller accordingto claim 19, wherein the processor is further configured to send, viathe control interface, an identifier of the client interface script tothe gateway.
 21. The policy controller according to claim 19, whereinthe policy controller is configured to receive information generated byexecution of the client interface script and generate, on the basis ofthe information a traffic handling rule.